Building management system with semantic model integration

ABSTRACT

A building management system (BMS) includes memory devices having instructions stored thereon that, when executed by processors, cause the processors to perform operations including obtaining a BMS ontology data model defining a plurality of BMS model classes and relationships between the BMS model classes, assigning a BMS model class selected from the plurality of BMS model classes to a plurality of BMS object definitions, generating a semantic site model by classifying a plurality of BMS objects associated with a building site according to the BMS object definitions and the BMS model classes assigned thereto, and transmitting a notification using the semantic site model.

CROSS-REFERENCES TO RELATED PATENT APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 17/039,364 filed Sep. 30, 2020, the entirety of which is incorporated by reference herein.

BACKGROUND

The present disclosure relates generally to the field of building management systems (BMSs), and more particularly to standardizing a BMS using a semantic model. A BMS is, in general, a system of devices configured to control, monitor, and manage equipment in or around a building. A BMS can include, for example, a HVAC system, a security system, a lighting system, a fire alerting system, any other system that is capable of managing building functions or devices, or any combination thereof. Equipment, spaces, and points associated with the BMS can be represented as objects in a BMS configuration dataset. To facilitate user interaction with a BMS, it may be desirable to map BMS objects to an ontology data model such that the BMS objects and object relationships are described in a semantic or natural manner.

SUMMARY

One embodiment of the present disclosure is a building management system (BMS). The BMS includes one or more memory devices having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to perform operations including obtaining a BMS ontology data model defining a plurality of BMS model classes and relationships between the BMS model classes, obtaining a plurality of BMS object definitions including equipment definitions defining a plurality of different types of equipment and point definitions defining a plurality of different types of points, assigning a BMS model class to each of the plurality of BMS object definitions, where the BMS model class is a semantic identifier selected from the plurality of BMS model classes defined by the BMS ontology data model, generating a semantic site model by classifying a plurality of BMS objects associated with a building site according to the BMS object definitions and the BMS model classes assigned thereto, and controlling building equipment using the semantic site model.

In some embodiments, the operations further include receiving a user input indicating one or more user-defined object identifiers associated with a first BMS object definition of the plurality of BMS object definitions. In some embodiments, classifying the plurality of BMS object includes identifying a subset of the plurality of BMS objects that satisfy at least one of the user-defined object identifiers and classifying the subset of the plurality of BMS object as the BMS model class assigned to the first BMS object definition.

In some embodiments, the operations further include analyzing configuration data for the BMS to identify a subset of the plurality of BMS objects that satisfy each of the plurality of BMS object definitions. In some embodiments, each of the plurality of BMS objects are classified as the BMS model class assigned to a corresponding BMS object definition.

In some embodiments, assigning the BMS model class to each of the plurality of BMS object definitions further includes receiving a user selection of the BMS model class for each of the BMS object definitions and assigning the BMS model class to each of the plurality of BMS object definitions based on the user selection.

In some embodiments, the BMS objects associated with the building site include at least one of equipment objects representing specific building equipment and point objects representing specific points in the BMS.

In some embodiments, the BMS objects associated with the building site include space objects representing specific spaces in the building site and where the plurality of BMS object definitions further include space definitions defining a plurality of different spaces.

In some embodiments, the operations further include obtaining a fault detection rule for the building site, the fault detection rule including one or more fault criteria defined without reference to one or more particular BMS objects needed to evaluate the fault criteria, using the semantic site model to identify the particular BMS objects needed to evaluate the fault criteria, and detecting a fault condition by evaluating the one or more fault criteria using data associated with the particular BMS objects.

In some embodiments, evaluating the fault criteria includes comparing a value provided by one or more of the particular BMS objects against a threshold.

Another embodiment of the present disclosure is a method including obtaining a BMS ontology data model defining a plurality of building management system (BMS) model classes and relationships between the BMS model classes, obtaining a plurality of BMS object definitions including equipment definitions defining a plurality of different types of equipment and point definitions defining a plurality of different types of points, assigning a BMS model class to each of the plurality of BMS object definitions, where the BMS model class is a semantic identifier selected from the plurality of BMS model classes defined by the BMS ontology data model, generating a semantic site model by classifying a plurality of BMS objects associated with a building site according to the BMS object definitions and the BMS model classes assigned thereto, and controlling building equipment using the semantic site model.

In some embodiments, the method further includes receiving a user input indicating one or more user-defined object identifiers associated with a first BMS object definition of the plurality of BMS object definitions. In some embodiments, classifying the plurality of BMS object includes identifying a subset of the plurality of BMS objects that satisfy at least one of the user-defined object identifiers and classifying the subset of the plurality of BMS object as the BMS model class corresponding to the first BMS object definition.

In some embodiments, the method further includes analyzing configuration data for the BMS to identify a subset of the plurality of BMS objects that satisfy each of the plurality of BMS object definitions. In some embodiments, each of the plurality of BMS objects are classified as the BMS model class assigned to a corresponding BMS object definition.

In some embodiments, assigning the BMS model class to each of the plurality of BMS object definitions further includes receiving a user selection of the BMS model class for each of the BMS object definitions and assigning the BMS model class to each of the plurality of BMS object definitions based on the user selection.

In some embodiments, the BMS objects associated with the building site include at least one of equipment objects representing instances of building equipment and point objects representing specific points in the BMS.

In some embodiments, the BMS objects associated with the building site include space objects representing specific spaces in the building site and where the plurality of BMS object definitions further include space definitions defining a plurality of different spaces.

In some embodiments, the method further includes determining one or more fault detection rules for the building site, detecting a trigger condition based on the one or more fault detection rules, the trigger condition indicating a fault and a first BMS object associated with the fault, and identifying one or more additional BMS objects associated with the fault based on the semantic data model.

In some embodiments, the trigger condition includes an indication that one or more parameters associated with the first BMS object exceed a threshold.

In some embodiments, determining one or more additional BMS objects associated with the fault includes identifying a BMS model class associated with the first BMS object and identifying the one or more additional BMS objects based on the relationships between the BMS model classes.

Yet another embodiment of the present disclosure is a building management system (BMS). The BMS includes one or more memory devices having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to perform operations including generating a semantic site model by classifying a plurality of BMS objects associated with a building site according to a plurality of BMS object definitions, each BMS object definition including an equipment definition defining a type of equipment and at least one point definition defining a type of point, where each BMS object definition is assigned a BMS model class selected from a BMS ontology data model, obtaining a fault detection rule for the building site, the fault detection rule including one or more fault criteria defined without reference to one or more particular BMS objects needed to evaluate the fault criteria, using the semantic site model to identify the particular BMS objects needed to evaluate the fault criteria, detecting a fault condition by evaluating the one or more fault criteria using data associated with the particular BMS objects, and initiating an automated corrective action in response to detecting the fault condition.

In some embodiments, the operations further include obtaining the BMS ontology data model defining a plurality of BMS model classes and relationships between the BMS model classes, where the BMS model classes are semantic identifiers selected from the plurality of BMS model classes defined by the BMS ontology data model.

In some embodiments, the BMS objects associated with the building site include space objects representing specific spaces in the building site and where the plurality of BMS object definitions further include space definitions defining a plurality of different spaces

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects, aspects, features, and advantages of the disclosure will become more apparent and better understood by referring to the detailed description taken in conjunction with the accompanying drawings, in which like reference characters identify corresponding elements throughout. In the drawings, like reference numbers generally indicate identical, functionally similar, and/or structurally similar elements.

FIG. 1 is a drawing of a building equipped with a HVAC system, according to some embodiments.

FIG. 2 is a block diagram of a waterside system that may be used in conjunction with the building of FIG. 1, according to some embodiments.

FIG. 3 is a block diagram of an airside system that may be used in conjunction with the building of FIG. 1, according to some embodiments.

FIG. 4 is a block diagram of a building management system (BMS) that may be used to monitor and/or control the building of FIG. 1, according to some embodiments.

FIG. 5 is a block diagram of another BMS which can be used to monitor and control the building of FIG. 1, according to some embodiments.

FIG. 6 is a block diagram of a semantic modeling system, according to some embodiments.

FIGS. 7A and 7B are block diagrams of a semantic modeling architecture, according to some embodiments.

FIG. 8 is a flowchart of a process for generating a semantic site model, according to some embodiments.

FIG. 9 is a flowchart of a process for fault detection and diagnostics using a semantic site model, according to some embodiments.

FIGS. 10A-10C show an example interface for viewing and modifying BMS object definitions, according to some embodiments.

FIGS. 11A-11B show an example interface for defining a selecting a model class for a BMS object definition, according to some embodiments.

DETAILED DESCRIPTION

Building HVAC Systems and Building Management Systems

Referring now to FIGS. 1-5, several building management systems (BMS) and HVAC systems in which the systems and methods of the present disclosure can be implemented are shown, according to some embodiments. In brief overview, FIG. 1 shows a building 10 equipped with a HVAC system 100. FIG. 2 is a block diagram of a waterside system 200 which can be used to serve building 10. FIG. 3 is a block diagram of an airside system 300 which can be used to serve building 10. FIG. 4 is a block diagram of a BMS which can be used to monitor and control building 10. FIG. 5 is a block diagram of another BMS which can be used to monitor and control building 10.

Referring particularly to FIG. 1, a perspective view of a building 10 is shown. Building 10 is served by a BMS. A BMS is, in general, a system of devices configured to control, monitor, and manage equipment in or around a building or building area. A BMS can include, for example, a HVAC system, a security system, a lighting system, a fire safety system, any other system that is capable of managing building functions or devices, or any combination thereof.

The BMS that serves building 10 includes an HVAC system 100. HVAC system 100 can include a plurality of HVAC devices (e.g., heaters, chillers, air handling units, pumps, fans, thermal energy storage, etc.) configured to provide heating, cooling, ventilation, or other services for building 10. For example, HVAC system 100 is shown to include a waterside system 120 and an airside system 130. Waterside system 120 can provide a heated or chilled fluid to an air handling unit of airside system 130. Airside system 130 can use the heated or chilled fluid to heat or cool an airflow provided to building 10. An exemplary waterside system and airside system which can be used in HVAC system 100 are described in greater detail with reference to FIGS. 2-3.

HVAC system 100 is shown to include a chiller 102, a boiler 104, and a rooftop air handling unit (AHU) 106. Waterside system 120 can use boiler 104 and chiller 102 to heat or cool a working fluid (e.g., water, glycol, etc.) and can circulate the working fluid to AHU 106. In various embodiments, the HVAC devices of waterside system 120 can be located in or around building 10 (as shown in FIG. 1) or at an offsite location such as a central plant (e.g., a chiller plant, a steam plant, a heat plant, etc.). The working fluid can be heated in boiler 104 or cooled in chiller 102, depending on whether heating or cooling is required in building 10. Boiler 104 can add heat to the circulated fluid, for example, by burning a combustible material (e.g., natural gas) or using an electric heating element. Chiller 102 can place the circulated fluid in a heat exchange relationship with another fluid (e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) to absorb heat from the circulated fluid. The working fluid from chiller 102 and/or boiler 104 can be transported to AHU 106 via piping 108.

AHU 106 can place the working fluid in a heat exchange relationship with an airflow passing through AHU 106 (e.g., via one or more stages of cooling coils and/or heating coils). The airflow can be, for example, outside air, return air from within building 10, or a combination of both. AHU 106 can transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example, AHU 106 can include one or more fans or blowers configured to pass the airflow over or through a heat exchanger containing the working fluid. The working fluid can then return to chiller 102 or boiler 104 via piping 110.

Airside system 130 can deliver the airflow supplied by AHU 106 (i.e., the supply airflow) to building 10 via air supply ducts 112 and can provide return air from building 10 to AHU 106 via air return ducts 114. In some embodiments, airside system 130 includes multiple variable air volume (VAV) units 116. For example, airside system 130 is shown to include a separate VAV unit 116 on each floor or zone of building 10. VAV units 116 can include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building 10. In other embodiments, airside system 130 delivers the supply airflow into one or more zones of building 10 (e.g., via supply ducts 112) without using intermediate VAV units 116 or other flow control elements. AHU 106 can include various sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure attributes of the supply airflow. AHU 106 can receive input from sensors located within AHU 106 and/or within the building zone and can adjust the flow rate, temperature, or other attributes of the supply airflow through AHU 106 to achieve setpoint conditions for the building zone.

In FIG. 2, waterside system 200 is shown as a central plant having a plurality of subplants 202-212. Subplants 202-212 are shown to include a heater subplant 202, a heat recovery chiller subplant 204, a chiller subplant 206, a cooling tower subplant 208, a hot thermal energy storage (TES) subplant 210, and a cold thermal energy storage (TES) subplant 212. Subplants 202-212 consume resources (e.g., water, natural gas, electricity, etc.) from utilities to serve the thermal energy loads (e.g., hot water, cold water, heating, cooling, etc.) of a building or campus. For example, heater subplant 202 may be configured to heat water in a hot water loop 214 that circulates the hot water between heater subplant 202 and building 10. Chiller subplant 206 may be configured to chill water in a cold water loop 216 that circulates the cold water between chiller subplant 206 building 10. Heat recovery chiller subplant 204 may be configured to transfer heat from cold water loop 216 to hot water loop 214 to provide additional heating for the hot water and additional cooling for the cold water. Condenser water loop 218 may absorb heat from the cold water in chiller subplant 206 and reject the absorbed heat in cooling tower subplant 208 or transfer the absorbed heat to hot water loop 214. Hot TES subplant 210 and cold TES subplant 212 may store hot and cold thermal energy, respectively, for subsequent use.

Hot water loop 214 and cold water loop 216 may deliver the heated and/or chilled water to air handlers located on the rooftop of building 10 (e.g., AHU 106) or to individual floors or zones of building 10 (e.g., VAV units 116). The air handlers push air past heat exchangers (e.g., heating coils or cooling coils) through which the water flows to provide heating or cooling for the air. The heated or cooled air may be delivered to individual zones of building 10 to serve the thermal energy loads of building 10. The water then returns to subplants 202-212 to receive further heating or cooling.

Although subplants 202-212 are shown and described as heating and cooling water for circulation to a building, it is understood that any other type of working fluid (e.g., glycol, CO2, etc.) may be used in place of or in addition to water to serve the thermal energy loads. In other embodiments, subplants 202-212 may provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations to waterside system 200 are within the teachings of the present invention.

Each of subplants 202-212 may include a variety of equipment configured to facilitate the functions of the subplant. For example, heater subplant 202 is shown to include a plurality of heating elements 220 (e.g., boilers, electric heaters, etc.) configured to add heat to the hot water in hot water loop 214. Heater subplant 202 is also shown to include several pumps 222 and 224 configured to circulate the hot water in hot water loop 214 and to control the flow rate of the hot water through individual heating elements 220. Chiller subplant 206 is shown to include a plurality of chillers 232 configured to remove heat from the cold water in cold water loop 216. Chiller subplant 206 is also shown to include several pumps 234 and 236 configured to circulate the cold water in cold water loop 216 and to control the flow rate of the cold water through individual chillers 232.

Heat recovery chiller subplant 204 is shown to include a plurality of heat recovery heat exchangers 226 (e.g., refrigeration circuits) configured to transfer heat from cold water loop 216 to hot water loop 214. Heat recovery chiller subplant 204 is also shown to include several pumps 228 and 230 configured to circulate the hot water and/or cold water through heat recovery heat exchangers 226 and to control the flow rate of the water through individual heat recovery heat exchangers 226. Cooling tower subplant 208 is shown to include a plurality of cooling towers 238 configured to remove heat from the condenser water in condenser water loop 218. Cooling tower subplant 208 is also shown to include several pumps 240 configured to circulate the condenser water in condenser water loop 218 and to control the flow rate of the condenser water through individual cooling towers 238.

Hot TES subplant 210 is shown to include a hot TES tank 242 configured to store the hot water for later use. Hot TES subplant 210 may also include one or more pumps or valves configured to control the flow rate of the hot water into or out of hot TES tank 242. Cold TES subplant 212 is shown to include cold TES tanks 244 configured to store the cold water for later use. Cold TES subplant 212 may also include one or more pumps or valves configured to control the flow rate of the cold water into or out of cold TES tanks 244.

In some embodiments, one or more of the pumps in waterside system 200 (e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines in waterside system 200 include an isolation valve associated therewith. Isolation valves may be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows in waterside system 200. In various embodiments, waterside system 200 may include more, fewer, or different types of devices and/or subplants Based on the particular configuration of waterside system 200 and the types of loads served by waterside system 200.

Referring now to FIG. 3, a block diagram of an airside system 300 is shown, according to some embodiments. In various embodiments, airside system 300 may supplement or replace airside system 130 in HVAC system 100 or may be implemented separate from HVAC system 100. When implemented in HVAC system 100, airside system 300 may include a subset of the HVAC devices in HVAC system 100 (e.g., AHU 106, VAV units 116, ducts 112-114, fans, dampers, etc.) and may be located in or around building 10. Airside system 300 may operate to heat or cool an airflow provided to building 10 using a heated or chilled fluid provided by waterside system 200.

In FIG. 3, airside system 300 is shown to include an economizer-type air handling unit (AHU) 302. Economizer-type AHUs vary the amount of outside air and return air used by the air handling unit for heating or cooling. For example, AHU 302 may receive return air 304 from building zone 306 via return air duct 308 and may deliver supply air 310 to building zone 306 via supply air duct 312. In some embodiments, AHU 302 is a rooftop unit located on the roof of building 10 (e.g., AHU 106 as shown in FIG. 1) or otherwise positioned to receive both return air 304 and outside air 314. AHU 302 may be configured to operate exhaust air damper 316, mixing damper 318, and outside air damper 320 to control an amount of outside air 314 and return air 304 that combine to form supply air 310. Any return air 304 that does not pass through mixing damper 318 may be exhausted from AHU 302 through exhaust damper 316 as exhaust air 322.

Each of dampers 316-320 may be operated by an actuator. For example, exhaust air damper 316 may be operated by actuator 324, mixing damper 318 may be operated by actuator 326, and outside air damper 320 may be operated by actuator 328. Actuators 324-328 may communicate with an AHU controller 330 via a communications link 332. Actuators 324-328 may receive control signals from AHU controller 330 and may provide feedback signals to AHU controller 330. Feedback signals may include, for example, an indication of a current actuator or damper position, an amount of torque or force exerted by the actuator, diagnostic information (e.g., results of diagnostic tests performed by actuators 324-328), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that may be collected, stored, or used by actuators 324-328. AHU controller 330 may be an economizer controller configured to use one or more control algorithms (e.g., state-Based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control actuators 324-328.

Still referring to FIG. 3, AHU 302 is shown to include a cooling coil 334, a heating coil 336, and a fan 338 positioned within supply air duct 312. Fan 338 may be configured to force supply air 310 through cooling coil 334 and/or heating coil 336 and provide supply air 310 to building zone 306. AHU controller 330 may communicate with fan 338 via communications link 340 to control a flow rate of supply air 310. In some embodiments, AHU controller 330 controls an amount of heating or cooling applied to supply air 310 by modulating a speed of fan 338.

Cooling coil 334 may receive a chilled fluid from waterside system 200 (e.g., from cold water loop 216) via piping 342 and may return the chilled fluid to waterside system 200 via piping 344. Valve 346 may be positioned along piping 342 or piping 344 to control a flow rate of the chilled fluid through cooling coil 334. In some embodiments, cooling coil 334 includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of cooling applied to supply air 310.

Heating coil 336 may receive a heated fluid from waterside system 200 (e.g., from hot water loop 214) via piping 348 and may return the heated fluid to waterside system 200 via piping 350. Valve 352 may be positioned along piping 348 or piping 350 to control a flow rate of the heated fluid through heating coil 336. In some embodiments, heating coil 336 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of heating applied to supply air 310.

Each of valves 346 and 352 may be controlled by an actuator. For example, valve 346 may be controlled by actuator 354 and valve 352 may be controlled by actuator 356. Actuators 354-356 may communicate with AHU controller 330 via communications links 358-360. Actuators 354-356 may receive control signals from AHU controller 330 and may provide feedback signals to controller 330. In some embodiments, AHU controller 330 receives a measurement of the supply air temperature from a temperature sensor 362 positioned in supply air duct 312 (e.g., downstream of cooling coil 334 and/or heating coil 336). AHU controller 330 may also receive a measurement of the temperature of building zone 306 from a temperature sensor 364 located in building zone 306.

In some embodiments, AHU controller 330 operates valves 346 and 352 via actuators 354-356 to modulate an amount of heating or cooling provided to supply air 310 (e.g., to achieve a setpoint temperature for supply air 310 or to maintain the temperature of supply air 310 within a setpoint temperature range). The positions of valves 346 and 352 affect the amount of heating or cooling provided to supply air 310 by cooling coil 334 or heating coil 336 and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU controller 330 may control the temperature of supply air 310 and/or building zone 306 by activating or deactivating coils 334-336, adjusting a speed of fan 338, or a combination of both.

Still referring to FIG. 3, airside system 300 is shown to include a building management system (BMS) controller 366 and a client device 368. BMS controller 366 may include one or more computer systems (e.g., servers, supervisory controllers, subsystem controllers, etc.) that serve as system level controllers, application or data servers, head nodes, or master controllers for airside system 300, waterside system 200, HVAC system 100, and/or other controllable systems that serve building 10. BMS controller 366 may communicate with multiple downstream building systems or subsystems (e.g., HVAC system 100, a security system, a lighting system, waterside system 200, etc.) via a communications link 370 according to like or disparate protocols (e.g., LON, BACnet, etc.). In various embodiments, AHU controller 330 and BMS controller 366 may be separate (as shown in FIG. 3) or integrated. In an integrated implementation, AHU controller 330 may be a software module configured for execution by a processor of BMS controller 366.

In some embodiments, AHU controller 330 receives information from BMS controller 366 (e.g., commands, setpoints, operating boundaries, etc.) and provides information to BMS controller 366 (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example, AHU controller 330 may provide BMS controller 366 with temperature measurements from temperature sensors 362-364, equipment on/off states, equipment operating capacities, and/or any other information that can be used by BMS controller 366 to monitor or control a variable state or condition within building zone 306.

Client device 368 may include one or more human-machine interfaces or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-Based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc.) for controlling, viewing, or otherwise interacting with HVAC system 100, its subsystems, and/or devices. Client device 368 may be a computer workstation, a client terminal, a remote or local interface, or any other type of user interface device. Client device 368 may be a stationary terminal or a mobile device. For example, client device 368 may be a desktop computer, a computer server with a user interface, a laptop computer, a tablet, a smartphone, a PDA, or any other type of mobile or non-mobile device. Client device 368 may communicate with BMS controller 366 and/or AHU controller 330 via communications link 372.

Referring now to FIG. 4, a block diagram of a building management system (BMS) 400 is shown, according to some embodiments. BMS 400 may be implemented in building 10 to automatically monitor and control various building functions. BMS 400 is shown to include BMS controller 366 and a plurality of building subsystems 428. Building subsystems 428 are shown to include a building electrical subsystem 434, an information communication technology (ICT) subsystem 436, a security subsystem 438, a HVAC subsystem 440, a lighting subsystem 442, a lift/escalators subsystem 432, and a fire safety subsystem 430. In various embodiments, building subsystems 428 can include fewer, additional, or alternative subsystems. For example, building subsystems 428 may also or alternatively include a refrigeration subsystem, an advertising or signage subsystem, a cooking subsystem, a vending subsystem, a printer or copy service subsystem, or any other type of building subsystem that uses controllable equipment and/or sensors to monitor or control building 10. In some embodiments, building subsystems 428 include waterside system 200 and/or airside system 300, as described with reference to FIGS. 2-3.

Each of building subsystems 428 may include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem 440 may include many of the same components as HVAC system 100, as described with reference to FIGS. 1-3. For example, HVAC subsystem 440 may include a chiller, a boiler, any number of air handling units, economizers, field controllers, supervisory controllers, actuators, temperature sensors, and other devices for controlling the temperature, humidity, airflow, or other variable conditions within building 10. Lighting subsystem 442 may include any number of light fixtures, ballasts, lighting sensors, dimmers, or other devices configured to controllably adjust the amount of light provided to a building space. Security subsystem 438 may include occupancy sensors, video surveillance cameras, digital video recorders, video processing servers, intrusion detection devices, access control devices and servers, or other security-related devices.

Still referring to FIG. 4, BMS controller 366 is shown to include a communications interface 407 and a BMS interface 409. Interface 407 may facilitate communications between BMS controller 366 and external applications (e.g., monitoring and reporting applications 422, enterprise control applications 426, remote systems and applications 444, applications residing on client devices 448, etc.) for allowing user control, monitoring, and adjustment to BMS controller 366 and/or subsystems 428. Interface 407 may also facilitate communications between BMS controller 366 and client devices 448. BMS interface 409 may facilitate communications between BMS controller 366 and building subsystems 428 (e.g., HVAC, lighting security, lifts, power distribution, business, etc.).

Interfaces 407, 409 can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with building subsystems 428 or other external systems or devices. In various embodiments, communications via interfaces 407, 409 may be direct (e.g., local wired or wireless communications) or via a communications network 446 (e.g., a WAN, the Internet, a cellular network, etc.). For example, interfaces 407, 409 can include an Ethernet card and port for sending and receiving data via an Ethernet-Based communications link or network. In another example, interfaces 407, 409 can include a WiFi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces 407, 409 may include cellular or mobile phone communications transceivers. In one embodiment, communications interface 407 is a power line communications interface and BMS interface 409 is an Ethernet interface. In other embodiments, both communications interface 407 and BMS interface 409 are Ethernet interfaces or are the same Ethernet interface.

Still referring to FIG. 4, BMS controller 366 is shown to include a processing circuit 404 including a processor 406 and memory 408. Processing circuit 404 may be communicably connected to BMS interface 409 and/or communications interface 407 such that processing circuit 404 and the various components thereof can send and receive data via interfaces 407, 409. Processor 406 can be implemented as a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components.

Memory 408 (e.g., memory, memory unit, storage device, etc.) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present application. Memory 408 may be or include volatile memory or non-volatile memory. Memory 408 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present application. According to an exemplary embodiment, memory 408 is communicably connected to processor 406 via processing circuit 404 and includes computer code for executing (e.g., by processing circuit 404 and/or processor 406) one or more processes described herein.

In some embodiments, BMS controller 366 is implemented within a single computer (e.g., one server, one housing, etc.). In various other embodiments BMS controller 366 may be distributed across multiple servers or computers (e.g., that can exist in distributed locations). Further, while FIG. 4 shows applications 422 and 426 as existing outside of BMS controller 366, in some embodiments, applications 422 and 426 may be hosted within BMS controller 366 (e.g., within memory 408).

Still referring to FIG. 4, memory 408 is shown to include an enterprise integration layer 410, an automated measurement and validation (AM&V) layer 412, a demand response (DR) layer 414, a fault detection and diagnostics (FDD) layer 416, an integrated control layer 418, and a building subsystem integration later 420. Layers 410-420 may be configured to receive inputs from building subsystems 428 and other data sources, determine optimal control actions for building subsystems 428 Based on the inputs, generate control signals Based on the optimal control actions, and provide the generated control signals to building subsystems 428. The following paragraphs describe some of the general functions performed by each of layers 410-420 in BMS 400.

Enterprise integration layer 410 may be configured to serve clients or local applications with information and services to support a variety of enterprise-level applications. For example, enterprise control applications 426 may be configured to provide subsystem-spanning control to a graphical user interface (GUI) or to any number of enterprise-level business applications (e.g., accounting systems, user identification systems, etc.). Enterprise control applications 426 may also or alternatively be configured to provide configuration GUIs for configuring BMS controller 366. In yet other embodiments, enterprise control applications 426 can work with layers 410-420 to optimize building performance (e.g., efficiency, energy use, comfort, or safety) Based on inputs received at interface 407 and/or BMS interface 409.

Building subsystem integration layer 420 may be configured to manage communications between BMS controller 366 and building subsystems 428. For example, building subsystem integration layer 420 may receive sensor data and input signals from building subsystems 428 and provide output data and control signals to building subsystems 428. Building subsystem integration layer 420 may also be configured to manage communications between building subsystems 428. Building subsystem integration layer 420 translate communications (e.g., sensor data, input signals, output signals, etc.) across a plurality of multi-vendor/multi-protocol systems.

Demand response layer 414 may be configured to optimize resource usage (e.g., electricity use, natural gas use, water use, etc.) and/or the monetary cost of such resource usage in response to satisfy the demand of building 10. The optimization may be Based on time-of-use prices, curtailment signals, energy availability, or other data received from utility providers, distributed energy generation systems 424, from energy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or from other sources. Demand response layer 414 may receive inputs from other layers of BMS controller 366 (e.g., building subsystem integration layer 420, integrated control layer 418, etc.). The inputs received from other layers may include environmental or sensor inputs such as temperature, carbon dioxide levels, relative humidity levels, air quality sensor outputs, occupancy sensor outputs, room schedules, and the like. The inputs may also include inputs such as electrical use (e.g., expressed in kWh), thermal load measurements, pricing information, projected pricing, smoothed pricing, curtailment signals from utilities, and the like.

According to an exemplary embodiment, demand response layer 414 includes control logic for responding to the data and signals it receives. These responses can include communicating with the control algorithms in integrated control layer 418, changing control strategies, changing setpoints, or activating/deactivating building equipment or subsystems in a controlled manner. Demand response layer 414 may also include control logic configured to determine when to utilize stored energy. For example, demand response layer 414 may determine to begin using energy from energy storage 427 just prior to the beginning of a peak use hour.

In some embodiments, demand response layer 414 includes a control module configured to actively initiate control actions (e.g., automatically changing setpoints) which minimize energy costs Based on one or more inputs representative of or Based on demand (e.g., price, a curtailment signal, a demand level, etc.). In some embodiments, demand response layer 414 uses equipment models to determine an optimal set of control actions. The equipment models may include, for example, thermodynamic models describing the inputs, outputs, and/or functions performed by various sets of building equipment. Equipment models may represent collections of building equipment (e.g., subplants, chiller arrays, etc.) or individual devices (e.g., individual chillers, heaters, pumps, etc.).

Demand response layer 414 may further include or draw upon one or more demand response policy definitions (e.g., databases, XML, files, etc.). The policy definitions may be edited or adjusted by a user (e.g., via a graphical user interface) so that the control actions initiated in response to demand inputs may be tailored for the user's application, desired comfort level, particular building equipment, or Based on other concerns. For example, the demand response policy definitions can specify which equipment may be turned on or off in response to particular demand inputs, how long a system or piece of equipment should be turned off, what setpoints can be changed, what the allowable set point adjustment range is, how long to hold a high demand setpoint before returning to a normally scheduled setpoint, how close to approach capacity limits, which equipment modes to utilize, the energy transfer rates (e.g., the maximum rate, an alarm rate, other rate boundary information, etc.) into and out of energy storage devices (e.g., thermal storage tanks, battery banks, etc.), and when to dispatch on-site generation of energy (e.g., via fuel cells, a motor generator set, etc.).

Integrated control layer 418 may be configured to use the data input or output of building subsystem integration layer 420 and/or demand response later 414 to make control decisions. Due to the subsystem integration provided by building subsystem integration layer 420, integrated control layer 418 can integrate control activities of the subsystems 428 such that the subsystems 428 behave as a single integrated super-system. In an exemplary embodiment, integrated control layer 418 includes control logic that uses inputs and outputs from a plurality of building subsystems to provide greater comfort and energy savings relative to the comfort and energy savings that separate subsystems could provide alone. For example, integrated control layer 418 may be configured to use an input from a first subsystem to make an energy-saving control decision for a second subsystem. Results of these decisions can be communicated back to building subsystem integration layer 420.

Integrated control layer 418 is shown to be logically below demand response layer 414. Integrated control layer 418 may be configured to enhance the effectiveness of demand response layer 414 by enabling building subsystems 428 and their respective control loops to be controlled in coordination with demand response layer 414. This configuration may advantageously reduce disruptive demand response behavior relative to conventional systems. For example, integrated control layer 418 may be configured to assure that a demand response-driven upward adjustment to the setpoint for chilled water temperature (or another component that directly or indirectly affects temperature) does not result in an increase in fan energy (or other energy used to cool a space) that would result in greater total building energy use than was saved at the chiller.

Integrated control layer 418 may be configured to provide feedback to demand response layer 414 so that demand response layer 414 checks that constraints (e.g., temperature, lighting levels, etc.) are properly maintained even while demanded load shedding is in progress. The constraints may also include setpoint or sensed boundaries relating to safety, equipment operating limits and performance, comfort, fire codes, electrical codes, energy codes, and the like. Integrated control layer 418 is also logically below fault detection and diagnostics layer 416 and automated measurement and validation layer 412. Integrated control layer 418 may be configured to provide calculated inputs (e.g., aggregations) to these higher levels Based on outputs from more than one building subsystem.

Automated measurement and validation (AM&V) layer 412 may be configured to verify that control strategies commanded by integrated control layer 418 or demand response layer 414 are working properly (e.g., using data aggregated by AM&V layer 412, integrated control layer 418, building subsystem integration layer 420, FDD layer 416, or otherwise). The calculations made by AM&V layer 412 may be based on building system energy models and/or equipment models for individual BMS devices or subsystems. For example, AM&V layer 412 may compare a model-predicted output with an actual output from building subsystems 428 to determine an accuracy of the model.

Fault detection and diagnostics (FDD) layer 416 may be configured to provide on-going fault detection for building subsystems 428, building subsystem devices (i.e., building equipment), and control algorithms used by demand response layer 414 and integrated control layer 418. FDD layer 416 may receive data inputs from integrated control layer 418, directly from one or more building subsystems or devices, or from another data source. FDD layer 416 may automatically diagnose and respond to detected faults. The responses to detected or diagnosed faults may include providing an alert message to a user, a maintenance scheduling system, or a control algorithm configured to attempt to repair the fault or to work-around the fault.

FDD layer 416 may be configured to output a specific identification of the faulty component or cause of the fault (e.g., loose damper linkage) using detailed subsystem inputs available at building subsystem integration layer 420. In other exemplary embodiments, FDD layer 416 is configured to provide “fault” events to integrated control layer 418 which executes control strategies and policies in response to the received fault events. According to an exemplary embodiment, FDD layer 416 (or a policy executed by an integrated control engine or business rules engine) may shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or assure proper control response.

FDD layer 416 may be configured to store or access a variety of different system data stores (or data points for live data). FDD layer 416 may use some content of the data stores to identify faults at the equipment level (e.g., specific chiller, specific AHU, specific terminal unit, etc.) and other content to identify faults at component or subsystem levels. For example, building subsystems 428 may generate temporal (i.e., time-series) data indicating the performance of BMS 400 and the various components thereof. The data generated by building subsystems 428 may include measured or calculated values that exhibit statistical characteristics and provide information about how the corresponding system or process (e.g., a temperature control process, a flow control process, etc.) is performing in terms of error from its setpoint. These processes can be examined by FDD layer 416 to expose when the system begins to degrade in performance and alert a user to repair the fault before it becomes more severe.

Referring now to FIG. 5, a block diagram of another building management system (BMS) 500 is shown, according to some embodiments. BMS 500 can be used to monitor and control the devices of HVAC system 100, waterside system 200, airside system 300, building subsystems 428, as well as other types of BMS devices (e.g., lighting equipment, security equipment, etc.) and/or HVAC equipment.

BMS 500 provides a system architecture that facilitates automatic equipment discovery and equipment model distribution. Equipment discovery can occur on multiple levels of BMS 500 across multiple different communications busses (e.g., a system bus 554, zone buses 556-560 and 564, sensor/actuator bus 566, etc.) and across multiple different communications protocols. In some embodiments, equipment discovery is accomplished using active node tables, which provide status information for devices connected to each communications bus. For example, each communications bus can be monitored for new devices by monitoring the corresponding active node table for new nodes. When a new device is detected, BMS 500 can begin interacting with the new device (e.g., sending control signals, using data from the device) without user interaction.

Some devices in BMS 500 present themselves to the network using equipment models. An equipment model defines equipment object attributes, view definitions, schedules, trends, and the associated BACnet value objects (e.g., analog value, binary value, multistate value, etc.) that are used for integration with other systems. Some devices in BMS 500 store their own equipment models. Other devices in BMS 500 have equipment models stored externally (e.g., within other devices). For example, a zone coordinator 508 can store the equipment model for a bypass damper 528. In some embodiments, zone coordinator 508 automatically creates the equipment model for bypass damper 528 or other devices on zone bus 558. Other zone coordinators can also create equipment models for devices connected to their zone busses. The equipment model for a device can be created automatically based on the types of data points exposed by the device on the zone bus, device type, and/or other device attributes. Several examples of automatic equipment discovery and equipment model distribution are discussed in greater detail below.

Still referring to FIG. 5, BMS 500 is shown to include a system manager 502; several zone coordinators 506, 508, 510 and 518; and several zone controllers 524, 530, 532, 536, 548, and 550. System manager 502 can monitor data points in BMS 500 and report monitored variables to various monitoring and/or control applications. System manager 502 can communicate with client devices 504 (e.g., user devices, desktop computers, laptop computers, mobile devices, etc.) via a data communications link 574 (e.g., BACnet IP, Ethernet, wired or wireless communications, etc.). System manager 502 can provide a user interface to client devices 504 via data communications link 574. The user interface may allow users to monitor and/or control BMS 500 via client devices 504.

In some embodiments, system manager 502 is connected with zone coordinators 506-510 and 518 via a system bus 554. System manager 502 can be configured to communicate with zone coordinators 506-510 and 518 via system bus 554 using a master-slave token passing (MSTP) protocol or any other communications protocol. System bus 554 can also connect system manager 502 with other devices such as a constant volume (CV) rooftop unit (RTU) 512, an input/output module (TOM) 514, a thermostat controller 516 (e.g., a TEC5000 series thermostat controller), and a network automation engine (NAE) or third-party controller 520. RTU 512 can be configured to communicate directly with system manager 502 and can be connected directly to system bus 554. Other RTUs can communicate with system manager 502 via an intermediate device. For example, a wired input 562 can connect a third-party RTU 542 to thermostat controller 516, which connects to system bus 554.

System manager 502 can provide a user interface for any device containing an equipment model. Devices such as zone coordinators 506-510 and 518 and thermostat controller 516 can provide their equipment models to system manager 502 via system bus 554. In some embodiments, system manager 502 automatically creates equipment models for connected devices that do not contain an equipment model (e.g., IOM 514, third party controller 520, etc.). For example, system manager 502 can create an equipment model for any device that responds to a device tree request. The equipment models created by system manager 502 can be stored within system manager 502. System manager 502 can then provide a user interface for devices that do not contain their own equipment models using the equipment models created by system manager 502. In some embodiments, system manager 502 stores a view definition for each type of equipment connected via system bus 554 and uses the stored view definition to generate a user interface for the equipment.

Each zone coordinator 506-510 and 518 can be connected with one or more of zone controllers 524, 530-532, 536, and 548-550 via zone buses 556, 558, 560, and 564. Zone coordinators 506-510 and 518 can communicate with zone controllers 524, 530-532, 536, and 548-550 via zone busses 556-560 and 564 using a MSTP protocol or any other communications protocol. Zone busses 556-560 and 564 can also connect zone coordinators 506-510 and 518 with other types of devices such as variable air volume (VAV) RTUs 522 and 540, changeover bypass (COBP) RTUs 526 and 552, bypass dampers 528 and 546, and PEAK controllers 534 and 544.

Zone coordinators 506-510 and 518 can be configured to monitor and command various zoning systems. In some embodiments, each zone coordinator 506-510 and 518 monitors and commands a separate zoning system and is connected to the zoning system via a separate zone bus. For example, zone coordinator 506 can be connected to VAV RTU 522 and zone controller 524 via zone bus 556. Zone coordinator 508 can be connected to COBP RTU 526, bypass damper 528, COBP zone controller 530, and VAV zone controller 532 via zone bus 558. Zone coordinator 510 can be connected to PEAK controller 534 and VAV zone controller 536 via zone bus 560. Zone coordinator 518 can be connected to PEAK controller 544, bypass damper 546, COBP zone controller 548, and VAV zone controller 550 via zone bus 564.

A single model of zone coordinator 506-510 and 518 can be configured to handle multiple different types of zoning systems (e.g., a VAV zoning system, a COBP zoning system, etc.). Each zoning system can include a RTU, one or more zone controllers, and/or a bypass damper. For example, zone coordinators 506 and 510 are shown as Verasys VAV engines (VVEs) connected to VAV RTUs 522 and 540, respectively. Zone coordinator 506 is connected directly to VAV RTU 522 via zone bus 556, whereas zone coordinator 510 is connected to a third-party VAV RTU 540 via a wired input 568 provided to PEAK controller 534. Zone coordinators 508 and 518 are shown as Verasys COBP engines (VCEs) connected to COBP RTUs 526 and 552, respectively. Zone coordinator 508 is connected directly to COBP RTU 526 via zone bus 558, whereas zone coordinator 518 is connected to a third-party COBP RTU 552 via a wired input 570 provided to PEAK controller 544.

Zone controllers 524, 530-532, 536, and 548-550 can communicate with individual BMS devices (e.g., sensors, actuators, etc.) via sensor/actuator (SA) busses. For example, VAV zone controller 536 is shown connected to networked sensors 538 via SA bus 566. Zone controller 536 can communicate with networked sensors 538 using a MSTP protocol or any other communications protocol. Although only one SA bus 566 is shown in FIG. 5, it should be understood that each zone controller 524, 530-532, 536, and 548-550 can be connected to a different SA bus. Each SA bus can connect a zone controller with various sensors (e.g., temperature sensors, humidity sensors, pressure sensors, light sensors, occupancy sensors, etc.), actuators (e.g., damper actuators, valve actuators, etc.) and/or other types of controllable equipment (e.g., chillers, heaters, fans, pumps, etc.).

Each zone controller 524, 530-532, 536, and 548-550 can be configured to monitor and control a different building zone. Zone controllers 524, 530-532, 536, and 548-550 can use the inputs and outputs provided via their SA busses to monitor and control various building zones. For example, a zone controller 536 can use a temperature input received from networked sensors 538 via SA bus 566 (e.g., a measured temperature of a building zone) as feedback in a temperature control algorithm. Zone controllers 524, 530-532, 536, and 548-550 can use various types of control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control a variable state or condition (e.g., temperature, humidity, airflow, lighting, etc.) in or around building 10.

BMS with Semantic Modeling

Referring now to FIG. 6, a block diagram of a semantic modeling system 600 is shown, according to some embodiments. System 600 is generally configured to generate a semantic site model for a BMS based on a BMS ontology data model. The BMS ontology data model generally describes objects in a BMS (e.g., equipment, spaces, points) and object relationships in a semantic or natural manner (e.g., using a semantic description schema). A BMS ontology data model can be applied to a BMS through the mapping or classifying of building metadata to the BMS ontology data model. In this regard, the BMS ontology data model may “standardize” a BMS (e.g., the BMS configuration data) according to the BMS ontology data model, to provide for improved monitoring, reporting, and commanding of the BMS with minimal user interaction. Additionally, a standardized BMS may be more user friendly than other systems, by defining BMS object relationships in an easy-to-understand format.

System 600 is shown to include a processing circuit 602, which further includes a processor 604 and memory 610. It will be appreciated that these components can be implemented using a variety of different types and quantities of processors and memory. Processor 604 can be implemented as a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components.

Memory 610 (e.g., memory, memory unit, storage device, etc.) can include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the processes, layers and modules described in the present application. Memory 610 can be or include volatile memory or non-volatile memory. Memory 610 can include database components, object code components, script components, or any other type of information structure for supporting the activities and information structures described in the present application. According to an example embodiment, memory 610 is communicably connected to processor 604 via processing circuit 602 and includes computer code for executing (e.g., by processing circuit 602 and/or processor 604) one or more processes described herein.

In some embodiments, processing circuit 602 is implemented within a single computer (e.g., one server, one housing, etc.). In other embodiments processing circuit 602 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). In some embodiments, system 600 and/or processing circuit 602 is embodied in the BMS 400 as described above, and accordingly, processing circuit 602, processor 604, and/or memory 610 may be similar to or the same as processing circuit 404, processor 406 and/or memory 408 as described above. Additionally, in such embodiments, a portion of the components of memory 610, described below, may be embodied in the BMS 400.

In some embodiments, system 600 is a stand-alone device or component not embodied in the BMS 400, and therefore includes its own dedicated processing circuit 602, processor 604, and/or memory 610. In other embodiments, system 600 is embodied as a portion of the BMS 400, a differently arranged BMS, or a building automation system (BAS), and accordingly may share a processing circuit, processor, and/or memory with any of these other BMSs or BASs. In yet other embodiments, a portion of system 600 (e.g., certain components of memory 610, described below) may be implemented via a system configuration tool, as described below with respect to FIG. 7B. A system configuration tool may be implement prior to configuring a particular BMS or a particular building site (e.g., prior to construction of the building, prior to operating building equipment, prior to activating or implementing a BMS, etc.), for example. Accordingly certain components of memory 610 may be implemented prior to operating a BMS (e.g., BMS 400).

Memory 610 is shown to include an object definition generator 612. Object definition generator 612 is generally configured to obtain unmapped object definitions (e.g., from an object database 620), and to apply user preferences and an ontology data model to the unmapped object definitions. An unmapped object definition is generally an abstraction of an object associated with a BMS. For example, an unmapped object definition may include generic or unmodified parameters, identifiers, labels, etc., associated with a BMS object (e.g., equipment, a space, a point). In general, an unmapped object definition includes at least a name and an identifier. In some embodiments, the unmapped object definitions may be structured according to a first data schema (e.g., BACnet). Accordingly, the name and/or identifier for an unmapped object definition may not be in a semantic format. For example, the unmapped object definition may include parameters and/or identifiers in a machine language, or in a schema that is not configured to be human-readable.

In some embodiments, an unmapped object definition also includes a set of point definitions typically associated with the BMS object reprinted by the unmapped object definition. For example, an unmapped object definition for a chiller type BMS object may include a plurality of point definitions corresponding to points typically associated with a chiller (e.g., outlet water temperature, pump speed, pressure, etc.). Object database 620 may include a library of previously defined BMS object definitions associated with a variety of objects commonly found in a BMS. For example, object database 620 may include a library of unmapped object definitions corresponding to any of the building equipment described above (e.g., building subsystems 428), and to any of a plurality of spaces or points in a building site.

Object definition generator 612 may obtain an ontology data model 622 in order to generate mapped object definitions from the unmapped object definitions. Ontology data model 622 is generally a common data model that defines BMS objects according to a semantic description schema. Ontology data model 622 may include standardized names, types, parameters, etc., for a variety of objects found in a BMS (e.g., spaces, equipment, and points). Ontology data model 622 can include a tag library comprising a set of tags that may be applied to unmapped object definitions. The tags may include semantic descriptions corresponding to each of the parameters of an object definition. For example, the tags may include semantic (i.e., plain language) labels, short names, search criteria, etc., that may be applied to an unmapped object definition. Ontology data model 622 may also define standardized parameters for each type of tag stored in the tag library. Further, ontology data model 622 may define relationships between tags. Accordingly, applying ontology data model 622 to unmapped object definitions may not only translate the unmapped object definitions into a common and/or semantic description schema, but ontology data model 622 may also define relationships between object definitions semantically. For example, ontology data model 622 may indicate that an object definition for a chiller “serves” an object definition for an air handler. In some embodiments, ontology data model 622 is retrieved from a semantic model database, as described in any of U.S. patent application Ser. No. 16/379,646, U.S. patent application Ser. No. 16/379,652, U.S. patent application Ser. No. 16/379,661, or U.S. patent application Ser. No. 16/379,666, all of which are incorporated herein by reference in their entireties.

Object definition generator 612 may be configured to generate mapped object definitions from the unmapped object definitions by applying user preferences and/or the ontology data model 622 to one or more unmapped object definitions. To achieve this, object definition generator 612 may analyze the various unmapped object definitions to identify, for each unmapped object definition, an object name or other similar identifier. Based on the object name, object definition generator 612 may determine a corresponding tag or tag set from the ontology data model 622, and may apply or map the tag or tag set to the unmapped object definition. In some embodiments, this also includes applying any user preferences to the unmapped object. The user preferences may include user-define identifiers or labels for certain object definitions, and in some cases can include a model class for certain object definitions.

Memory 610 is also shown to include a classification engine 614, configured to identify BMS objects from BMS configuration data and to classify the BMS objects based on the mapped object definitions generated by object definition generator 612. More specifically, classification engine 614 may classify BMS objects identified from the BMS configuration data by identifying one or more BMS objects that satisfy (i.e., match) a mapped object definition in the semantic model, and by classifying or mapping the one or more identified BMS objects to the mapped object definition. In this regard, any parameters of the mapped object definition (e.g., associated point definitions) may also be associated with the one or more identified BMS objects. For example, the one or more BMS object may be classified according to a model class assigned to the mapped object definition and/or the point definitions associated with the mapped object definition. A semantic site model may be generated for a BMS or a building site based on this classification of the BMS objects associated with the BMS or building site according to the mapped object definitions and assigned model classes. In some embodiments, the semantic site model is generated in a similar manner to the semantic models described in any of U.S. patent application Ser. No. 16/379,646, U.S. patent application Ser. No. 16/379,652, U.S. patent application Ser. No. 16/379,661, or U.S. patent application Ser. No. 16/379,666, mentioned above.

In some embodiments, classification engine 614 is also configured to obtain configuration data for a BMS by scanning, mining, or otherwise analyzing a BMS (e.g., BMS 400) to detect and identify BMS objects such as equipment, spaces (e.g., floors, rooms, levels, etc.), and/or points associated with the BMS. For example, classification engine 614 may mine a BMS to identify equipment (e.g., HVAC equipment) and to identify spaces served by the equipment. In this regard, classification engine 614 may be configured to generate and/or update the BMS configuration based on the identification of BMS objects.

Memory 610 is also shown to include a fault detection and diagnostics (FDD) engine 616. FDD engine 616 is configured to determine one or more fault detection and/or diagnostic rules for a BMS, and to monitor the BMS to detect faults or perform diagnostic procedures. In some embodiments, FDD engine 616 is structured in a similar manner to the fault detection system described in U.S. Pat. No. 8,788,097, incorporated herein by reference in its entirety. FDD engine 616 may obtain fault detection or diagnostic rules from a user input, for example, or may obtain the rule by any other method (e.g., from a database).

FDD engine 616 may also be configured to monitor operating data corresponding to equipment, spaces, and/or points of a BMS. Said data may include, for example, current operating states or parameters, sensor or meter readings, etc. FDD engine 616 can compare the received data with the fault detection and diagnostic rules to detect a fault condition. A fault condition may indicate that a particular BMS object meets one or more fault criteria, which may in turn indicate an issue with one or more BMS objects (e.g., equipment). As an example, a fault detection and diagnostic rule may define a desired temperature range for a space in a building site. If FDD engine 616 determines that the air temperature within the space exceeds a threshold corresponding to the desire temperature range (e.g., based on sensor data), FDD engine 616 may indicate a fault.

In some embodiments, FDD engine 616 may utilize a previously generated semantic site model to identify BMS objects associated with a fault detection rule. Specifically, for each application or implementation of a fault detection rule, FDD engine 616 can determine one or more BMS object needed to evaluate the rule using the semantic site model. The BMS objects may be identified based on the fault criteria for each fault detection rule. For example, the fault criteria may require a particular type of sensor measurement, a particular value, etc. When the fault detection rule is applied to a particular space, equipment, or point of a BMS or a building, the semantic site model may be used to identify the particular BMS objects that are referenced to determine the fault criteria.

In some embodiments, FDD engine 616 may also initiate automated corrective actions based on a detected fault condition. In some embodiments, a corrective action may be predetermined based on the type of fault condition, the fault detection rule, the BMS objects associated with the fault condition, etc. The corrective action may include, for example, controlling building equipment associated with the BMS objects in order to affect one or more parameters associated with the BMS objects. The corrective action can also include generating and transmitting a notification or a work order based on the detected fault.

A user interface generator 618 is configured to generate graphical user interfaces relating system 600. For example, user interface generator 618 may generate a graphical user interface for the user to enter preferences for a mapping object definitions, as discussed above with respect to object definition generator 612. In some embodiments, user interface generator 618 may provide a user interface to allow the user to define or select a model class for one or more object definitions. User interface generator 618 may also generate interfaces that allow a user to interact with a BMS (e.g., BMS 400), particularly after the BMS's configuration data has been classified according to mapped object definitions, as discussed above. It will be appreciated, however, that user interface generator 618 may be generally configured to generate any sort of graphical user interface.

Still referring to FIG. 6, system 600 is shown to include a communications interface 630. Processing circuit 602 can be communicably connected to communications interface 630 such that processing circuit 602 and the components thereof can send and receive data via the communications interface 630. System 600 may exchange data with network 446 and/or user device 632 via a communications interface 630, for example. Communications interface 630 may include a wired and/or wireless interface for connecting system 600 to network 446 and/or a user device 632. For example, communications interface 630 may include a wireless network adaptor for wirelessly connecting system 600 to network 446. In some embodiments, communications interface 630 also provides an interface between system 600, and any one or more the building subsystems 428, or other components of the BMS 400 or BMS 500 described above. In this regard, communications interface 630 can include a BACnet interface in addition to other types of communications interfaces (e.g., Modbus, LonWorks, DeviceNet, XML, etc.).

User device 632 may be any electronic device that allows a user to interact with system 600 through a user interface. Examples of user devices include, but are not limited to, mobile phones, electronic tablets, laptops, desktop computers, workstations, and other types of electronic devices. User device 632 may be similar to client device 368 and/or client devices 504, as described above. User device 632 may display graphical user interfaces or other data on a display, thereby enabling a user to easily view data and interact with system 600. For example, user device 632 may present any of the user interfaces generated by user interface generator 618.

Referring now to FIG. 7A, a block diagram of a semantic modeling architecture 700 is shown, according to some embodiments. Architecture 700 may be implemented by system 600, for example, and accordingly may illustrate the generation of a semantic site model by system 600. Architecture 700 is shown to include unmapped object definitions 702 and user preferences 704. Unmapped object definitions 702 can include one or more objects, data sets, files, etc., corresponding to one or more BMS object definitions, as described above with respect to FIG. 6. Similarly, user preferences 704 can include one or more individual settings, files, data sets, etc., that define user preferences. In general, user preferences 704 may include at least an indication of a model class to assign to each of one or more BMS object definitions. In some embodiments, user preferences 704 also include user selections of other object definition parameters, including BMS object labels, configuration settings, point definition labels, point definition short names (i.e., identifiers), and/or point definition search criteria.

Unmapped object definitions 702 and user preferences 704 may be obtained by, or fed into, object definition generator 612, along with ontology data model 622. As described above, object definition generator 612 may apply ontology data model 622 and/or user preferences 704 to unmapped object definitions 702. For example, object definition generator 612 may map the unmapped object definitions 702 to corresponding object definitions in ontology data model 622, and may subsequently or concurrently apply user preferences 704 to add, remove, or modify one or more parameters of each object definition. In other words, unmapped object definitions 702, user preferences 704, and ontology data model 622 may be combined or married by object definition generator 612 to generate mapped object definitions 706. Mapped object definitions 706 may then be stored in object database 620.

As a non-limiting example, an unmapped object definition (e.g., one of unmapped object definitions 702) for a particular BMS object representing an AHU may be obtained by object definition generator 612, along with ontology data model 622. Ontology data model 622 may include a variety of standardized information for AHU objects, such as AHU parameters (e.g., temperatures, fan speed, capacity, etc.), along with a plurality of point definitions associated with an AHU object. Each point definition may represent a particular point, sensor, device, etc., associated with a physical AHU. For example, the AHU object may include point definitions for fan status, fan speed, output air temperature, etc. Additionally, ontology data model 622 may define a plurality of model classes that can be assigned to BMS objects, and may also indicate model class relationships. User preferences 704 may include at least a user selection of a model class to apply to AHU objects. Object definition generator 612 can map the unmapped AHU object to the ontology data model 622 and can assign user preferences 704 to AHU object.

Mapped object definitions 706 can be retrieved or transmitted from object database 620 to classification engine 614. Classification engine 614 may also obtain BMS configuration data 708 for a particular BMS and/or a particular building site, in order to apply mapped object definitions 706 to BMS configuration data 708. As described above with respect to FIG. 6, classification engine 614 may classify BMS configuration data 708, which can include objects corresponding to equipment, spaces, and/or points in a BMS (e.g., BMS 400), based on mapped object definitions 706. In other words, classification engine 614 can classify each BMS object of BMS configuration data 708 to a corresponding mapped object definition (e.g., one of mapped object definitions 706). Accordingly, each BMS object is also classified according to a model class assigned to a corresponding one of the mapped object definitions 706. The output of classification engine 614 is shown as a semantic site model 710. As described above, semantic site model 710 may be a model of a complete building site or a complete BMS that defines each BMS object associated with the site or BMS (e.g., each space, device, and/or point) according to mapped object definitions 706, and thereby according to ontology data model 622 and user preferences 704.

To continue the example above, the mapped object definition for the AHU can be retrieved from object database 620 by classification engine 614. Subsequently, configuration data for a first BMS that includes BMS objects for each of the equipment, spaces, and points within the first BMS may be obtain. The configuration data may be analyzed by classification engine 614 to identify any BMS objects that correspond to an AHU. The identified BMS objects may then be classified as, or mapped to, the mapped object definition for the AHU.

Referring now to FIG. 7B, an implementation of architecture 700 is shown, according to some embodiments. In particular, FIG. 7B shows various components of architecture 700 performed by a system configuration tool 720 and a BMS 740. As mentioned above, system configuration tool 720 may be a separate and/or remote system from a BMS (e.g., BMS 400), and/or may be a subsystem implemented within a BMS. In any case, system configuration tool 720 is generally configured to be implemented prior to operating a BMS (e.g., prior to construction of a building, prior to operating building equipment, etc.), in order to configure the BMS for operations. For example, system configuration tool 720 may be implemented prior to activating a BMS in order to configure BMS objects. In some embodiments, system configuration tool 720 is implemented when BMS 740 is offline, or when equipment of BMS 740 is disconnected.

System configuration tool 720 is show to include a processing circuit 722. Processing circuit 722 is shown to further include a processor 724 and memory 730. Similarly, BMS 740 is shown to include a processing circuit 742, further including a processor 744 and 730. It will be appreciated that BMS 740 may be substantially similar to, or the same as, either BMS 400 or BMS 500 described above. It will also be appreciated that these components can be implemented using a variety of different types and quantities of processors and memory. Processor 724 and/or processor 744 can be implemented as a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components.

Memory 730 and/or memory 750 (e.g., memory, memory unit, storage device, etc.) can include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the processes, layers and modules described in the present application. Memory 730 and/or memory 750 can be or include volatile memory or non-volatile memory. Memory 730 and/or memory 750 can include database components, object code components, script components, or any other type of information structure for supporting the activities and information structures described in the present application. In some embodiments, memory 730 and/or memory 750 are communicably connected to a corresponding one of processor 724 or processor 744 via processing circuit 722 or processing circuit 724. Each of memory 730 and memory 750 can include computer code for executing one or more processes described herein.

As shown, system configuration tool 720 may be configured to generate mapped object definitions 706 based on unmapped object definitions 702, user preferences 704, and ontology data model 622, as described above with respect to FIG. 7A. In this manner, mapped object definitions 706 may be generated prior to implementing, activating, or otherwise operating a BMS (e.g., BMS 740). For example, mapped object definitions 706 may be generated as part of a configuration process for BMS 740. Mapped object definitions 706 may be stored in object database 620 and subsequently transmitted to BMS 740 to generate semantic site model 710. In some embodiments, BMS 740 may receive mapped object definitions 706 as part of a configuration process, such as after implementing, activating, or otherwise operating BMS 740 and/or building equipment. For example, BMS 740 may receive mapped object definitions 706 after BMS 740 and any associated equipment is installed in a building, and after BMS 740 and/or the equipment is turned on or operated.

In some embodiments, BMS configuration data 708 is also generated once BMS 740 is activate or operated. For example, once BMS 740 is turned on and any associated equipment is connected, BMS 740 can be mined or analyzed to identify BMS objects corresponding to equipment, spaces, points, etc., as described above. The identified BMS objects and/or object relationships may be defined in BMS configuration data 708. BMS 740 may then classify BMS configuration data 708 according to mapped object definitions 706 in order to generate semantic site model 710, as described above. Semantic site model 710 may be referenced by a user of BMS 740 in subsequent operations.

Referring now to FIG. 8, a flowchart of a process 800 for generating a semantic site model is shown, according to some embodiments. Process 800 can be implemented by system 600 in order to generate a semantic model of a building or site served by BMS 400 or BMS 500, for example. As mentioned above, a semantic site model may beneficially “standardize” a BMS or building site according to a common data model. A standardized BMS may be easier for a user to understand and interact with, by describing BMS objects and object relationships semantically, and a semantic site model may decrease configuration time for new BMSs. Additionally, the semantic site model may classify BMS objects according to model classes to group BMS objects and to clearly identify BMS object relationships. It will be appreciated that certain steps of the process 800 may be optional and, in some embodiments, the process 800 may be implemented using less than all of the steps. In some embodiments, certain steps of process 800 may be performed by system configuration tool 720 and other steps may be performed by BMS 740, as described above with respect to FIG. 7B. For example, steps 802-806 can be performed by system configuration tool 720 while step 808-812 can be performed by BMS 740.

At step 802, a BMS ontology data model is obtained. As described above, the BMS ontology data model is generally a common data model that defines BMS objects according to a semantic description schema. The BMS ontology data model may include a tag library for describing a variety of objects found in a BMS (e.g., spaces, equipment, and points). The BMS ontology data model may also include a plurality of BMS model classes that can be assigned to various BMS objects and/or to various point definitions associated with a BMS object. A BMS model class is generally a semantic identifier that can be applied to a BMS object. For example, a BMS model class may indicate a type of equipment, space, or point.

At step 804, unmapped BMS object definitions are obtained. The unmapped BMS object definitions may be obtained from a database, for example. The unmapped BMS object definitions can include equipment definitions for a variety of different types of building equipment and/or point definitions for a variety of points associated with building equipment. An unmapped BMS object definition may be an abstracted representation of a particular type of building equipment, for example, and the unmapped BMS object definition may include a plurality of point definitions typically associated with the particular type of building equipment. For example, and as described in greater detail with respect to FIGS. 10A-10C, an unmapped BMS object definition for a VAV (e.g., VAV units 116) may include point definitions for zone air temperature, zone air setpoint, and supply fan status points. In some embodiments, the unmapped BMS object definitions can also include space definitions for a variety of different spaces within a building site, and can include additional point definitions for points associated with the different spaces.

At step 806, a BMS model class is assigned to each of the unmapped BMS object definitions. As described above, a model class is generally a semantic identifier that can be applied to a BMS object definition. Model classes can be used to classify or otherwise indicate a type of equipment, space, or point. For example, the model class may be a text sting or a label that identifies a class for a particular unmapped object definition, or for an equipment or a point definition associated with an unmapped object definition. In some embodiments, the BMS model class is automatically assigned to one or more unmapped BMS object definitions based on one or more parameters of the unmapped BMS object definitions. For example, search criteria (e.g., search terms), a short name, a type, a label, etc., associated with the unmapped BMS object definition may be identified, and a model class may be assigned based on any of the identified parameters.

In other embodiments, a user selection of a model class is received for each BMS object definition. For example, the user may select a model class from a list (e.g., based on the ontology data model) in order to assigned the selected model class to an unmapped BMS object definition. In some embodiments, a user may also defined one or more additional BMS object identifiers. In such embodiments, a user selection specifying one or more user-defined identifiers (e.g., short name, label, etc.) associated with a first unmapped BMS object definition may be received. The user selection of a model class and/or user defined identifiers for BMS object definitions is described in greater detail with respect to FIGS. 10A-11B.

In some embodiments, step 806 also includes applying the BMS ontology data model to the unmapped BMS object definitions. In some such embodiments, the BMS ontology data model is applied to the unmapped BMS object definitions concurrently with, or before or after, the model classes are assigned. As discussed above, mapped BMS object definitions are generated based on the assignment of model classes and/or the application of the BMS ontology data model. In other words, the previously unmapped BMS object definitions may be mapped to the BMS ontology data model in order to standardize the BMS object definitions, and the model classes are applied.

At step 808, a BMS is analyzed to identify BMS objects associated with a building site. In some embodiments, BMS configuration data can be mined, scanned, or otherwise analyzed to identify BMS object associated with a particular site. For example, the BMS configuration data is analyzed to determine the various spaces, points, and/or equipment associated with the building site and/or controlled by a BMS of the building site. BMS objects can include equipment entities representing specific instances of building equipment and point entities representing specific points in the BMS. BMS objects can also include space entities representing specific building spaces. In some embodiments, a BMS itself may be mined or analyzed in order to generate the configuration data.

At step 810, a semantic site model is generated by classifying the BMS objects based on the BMS object definitions and the model classes assigned to each of the BMS object definitions. In other words, the BMS object identified at step 808 may be classified or mapped to corresponding BMS object definitions, and thereby may be classified or mapped according to the model classes assigned to each BMS object definition. In some embodiments, BMS objects are classified according to an object identifier associated with each of the BMS object definitions. The object identifier may be a short name, a label, a number, or another type of identifier associated with each BMS object definition. For example, a first BMS object definition corresponding to a VAV type object may include a short name of “SF-S,” which corresponds to a supply fan status. The BMS objects identified at step 808 may be analyzed to detect any BMS objects that also include an identifier of “SF-S.” In some cases, search criteria may also be utilized to identify BMS objects. For example, the search criteria may include additional identifiers associated with a supply fan status. The BMS objects may also be analyzed to identify any BMS objects that include identifiers corresponding to the search criteria.

At step 812, building equipment is monitored and/or controlled based on the semantic site model. In some embodiments, the semantic site model is utilized to monitor equipment operations. In some embodiments, a user interface may be generated to present the semantic site model, or to present data associated with the semantic site model such as equipment or site operational data. In some embodiments, controlling the building equipment can include adjusting one or more operating parameters associated with the building equipment. For example, a setpoint may be modified for a particular building device. In any case, the semantic site model generated by process 800 may, advantageously, provide a user friendly method for interacting with a BMS. For example, the semantic site model defines BMS objects in a natural language that is easy for users to understand.

Additionally, the classification of BMS objects based on model classes and the relationships between BMS objects defined in the semantic site model can aid in system analytics or querying. Instead of searching for a BMS object by a string of characters or manually tracing equipment relationships, for example, a user may query the system (e.g., system 600) in a more natural way. For example, the user can ask the system simple questions, such as “what are the temperatures of all meeting rooms on the fourth floor?” Using the semantic site model, the system could search for BMS objects having a model class of “Zone Air Temperature” and could narrow the search to BMS objects related to spaces on the fourth floor of a building site. In this manner, the semantic site model may greatly increase user friendliness, and can also increase interoperability with other systems.

Referring now to FIG. 9, a flowchart of a process 900 for fault detection and diagnostics using a semantic site model is shown, according to some embodiments. Process 900 can be implemented by system 600 in order to facilitate fault detection and/or diagnostics for a BMS, for example. Process 900 may utilize a semantic site model to identify BMS objects associated with fault detection and diagnostic rules. In this regard, process 900 does not necessarily require that fault detection and diagnostics rules reference a particular BMS object. Advantageously, process 900 may allow for generic or non-site specific fault detection and diagnostic rules to be implemented and evaluated across a range of building sites or BMSs. It will be appreciated that certain steps of the process 900 may be optional and, in some embodiments, the process 900 may be implemented using less than all of the steps.

At step 902, at least one fault detection rule is obtained. The fault detection rule generally includes one or more fault criteria that are evaluated using BMS data (e.g., operating data) to detect fault conditions. Unlike fault detections rules for certain other systems, the fault detection rule obtain at step 902 does not include fault criteria that reference to a particular BMS object. In other words, the fault criteria are defined without reference to a particular BMS object. This allows the fault detection rule to be applied to any number of different building sites or BMSs, because the fault criteria do not rely on a particular BMS object. Additionally, the fault detections rule may be structured more broadly than other rules that rely on a particular object, and may be defined in a more natural way.

An example fault detection rule may include fault criteria such as “IF zone temperature is greater than a threshold AND a VAV damper position is closed” that, if true, may indicate a fault condition. In this example, the fault criteria variables of “zone temperature,” “threshold,” and “VAV damper position” can be defined in the fault detection rule without reference to the particular BMS object or objects that need to be analyzed in order to determine whether the fault detection rule is satisfied. For example, the particular temperature sensor corresponding to “zone temperature” and/or the particular VAV that supplies the “zone” or space do not need to be defined in the fault detection rule.

At step 904, a semantic site model (e.g., generated using process 800) is used to identify the particular BMS objects needed to evaluate the fault criteria. For example, the fault detection rule may be applied to a particular space or equipment of a BMS, and the semantic site model may be used to identify BMS object associated with the particular space or equipment. As described above, a single fault detection rule may advantageously be applied to multiple different building spaces, devices, points, etc. Accordingly, for each implementation or application of the fault detection rule, a new set of BMS objects may be identified to evaluate the fault criteria.

To continue the example above, the fault detection rule including fault criteria such as “IF zone temperature is greater than a threshold AND a VAV damper position is closed” could be applied to a particular building space (e.g., a room). The semantic site model could be be used to identify a specific zone temperature sensor that provides the “zone temperature” for the particular space, a particular threshold value, and a particular VAV or damper that controls airflow to the particular space. In this case, the relationships defined by the semantic site model may be used to identify the zone temperature sensor and/or VAV associated with the space, and the threshold value may be a parameter associated with a BMS object representing the particular space.

At step 906, a fault condition is detected by evaluating the fault criteria using data related to the particular BMS objects. Said data may include, for example, operational data or other data received from BMS objects represented in the semantic data model. For example, the data could include values from sensors or equipment within a building represented by the semantic site model. The received BMS object data may be compared to a value or a threshold for each fault criteria to determine if the fault criteria are “true” or “false.” Depending on the particular fault detection rule, a fault condition may be detected if one or more of the fault criteria are “true.” In some cases, multiple fault criteria or even all of the fault criteria may need to be “true” in order for a fault condition to be detected.

In the example above, the fault criteria may be evaluated by determining a reading (i.e., value) from the zone temperature sensor associated with the particular space, as identified using the semantic data model, and comparing the temperature sensor value to the threshold value obtained from the BMS object representing the particular space. Similarly, a value may be obtained from a sensor indicating a position of the damper for a VAV supplying the particular space, and the damper position may be analyzed to determine with the VAV damper position is “closed,” and therefore matches the fault criteria.

At step 908, an automated corrective action is initiated in response to detecting a fault condition. The automated corrective action may include one or more individual corrective actions. For example, the automated corrective action can include controlling building equipment. In some embodiments, equipment can be controlled by adjusting an operating parameter of the equipment, turning the equipment off, taking the equipment office, activating additional equipment, etc. Generally, the equipment are controlled to correct the detected fault condition. In other words, the equipment can be controlled to affect one or more parameters associated with the fault criteria. For example, if a zone temperature is above a threshold value, HVAC equipment may be operated to reduce the temperature of a space corresponding to the zone temperature.

In some embodiments, the automated corrective action can include generating a work order and/or scheduling a maintenance activity for faulty equipment. The work order or maintenance request can be transmitted to a work order computer system, for example, or may be transmitted to a user device (e.g., associated with a maintenance or service technician). In some embodiments, automated corrective action includes presenting an indication of the fault condition to a user (e.g., of user device 632). As an example, a notification or alert may be generated and transmitted to the user's device as a text message, an email, a voice call, a push notification, etc. In some embodiments, a fault indication is presented on a user interface of a BMS system (e.g., BMS 400).

In some embodiments, a diagnostic process may also be implemented to determine a cause of the fault condition. The diagnostic process may also rely on the semantic site model, and in particular may rely on the relationships between BMS objects as defined in the semantic site model. For example, while one or more BMS object may be directly associated with a fault condition (e.g., the BMS object identified at step 906), additional BMS objects may also be identified that have some sort of impact on the detected fault condition. The semantic model may be analyzed to identify, based on the BMS object relationships, additional BMS objects that may be affected by the fault condition, or may have been at least partially responsible for causing the fault condition.

Referring now to FIGS. 10A-10C, an interface 1000 for viewing and modifying a BMS object definition is shown, according to some embodiments. More specifically, interface 1000 may allow a user to edit an object definition by adding, removing, or otherwise modifying one or more point definitions associated with the object definition. In some embodiments, interface 1000 allows a user to select a model class for each point definition associated with the object definition. Interface 1000 may also allow a user to adjust point definition labels, identifiers, and other point definition parameters, as discussed below. Interface 1000 may be generated by user interface generator 618 and presented to a user viewing user device 632, for example.

In the example shown in FIGS. 10A-10C, interface 1000 includes a plurality of point definitions associated with a particular BMS object, in this case a VAV unit (e.g., VAV units 116). Interface 1000 also includes various parameters or information associated with each point definition. Specifically, each point definition is shown with a point label in a “Label” column 1002. The point labels in column 1002 may be semantic descriptions of points in a BMS that correspond to the various point definitions. Each point definition is also shown to include an identifier or a “short name,” listed in a “Short Name” column 1004, and a model class listed in a “Model Class” column 1006. Interface 1000 also includes a “Search Criteria” column 1008 that includes a number of search terms for each point definition. As shown in FIG. 10A, the example VAV unit entity object includes three points definition. As an example, a first point is shown as “Zone Air Temp,” with a short name of “ZN-T” and a model class of “ZONE TEMPERTURE.”

A user may select an “edit” button 1010 to add, remove, or modify point definition shown in interface 1000. Selecting button 1010 may dynamically modify interface 1000, as shown in FIG. 10B, to include a variety of control elements 1012. Control elements 1012 can include a plurality of button, icons, or other elements that facility adding, removing, or editing the various point definitions. For example, control elements 1012 can include separate buttons to add and remove point definitions, as well as buttons to navigate between the point definitions presented in interface 1000. The user may select a particular point definition, in this example “Zone Air Setpoint,” as shown in FIG. 10B, and may edit the selected point definition. For example, the user may edit the point definition's label, short name, search criteria, etc. The user may also assign a model class to the selected point definition.

When a user attempts to assign a model class to a selected point definition, the user may be presented via a second interface for selecting a previously defined model class (e.g., a model class defined in the ontology data model, as described above). As shown in FIGS. 11A-11B, for example, an example interface 1100 for selecting a model class may be presented. Interface 1100 may be presented as an overlay to interface 1000 or a pop-up window, or in some cases may be a separate interface that entirely replaces interface 1000. Interface 1100 may include a list of all possible model classes that the user may select. In some embodiments, interface 1100 includes a “type” or an identifier for each model class and a brief description of the model class.

As shown, a user may select an equipment type in a first graphical element 1102 of interface 1100. In some embodiments, element 1102 may be a text entry field, a drop-down menu, or any other suitable graphical element for identifying a particular equipment type. As discussed above, the equipment type may include any of a variety of equipment types defined in the ontology data model. In the example shown in FIG. 11A, the user has selected a VAV as the equipment type in element 1102. This selection corresponds to the type of equipment associated with the object definition being viewed and/or modified in example FIGS. 10A-10C.

After selecting an equipment type (e.g., VAV), the user may select a point purpose from a second graphical element 1104. Like element 1102, element 1104 may be a text entry field, a drop-down menu, or any other suitable graphical element for identifying a point purpose. In some embodiments, element 1104 may not be populated until a particular equipment type is selected in element 1102. For example, element 1104 may be a drop-down menu, and the particular point purpose selections listed in the drop-down menu may not be populated until an equipment type is selected. Accordingly, the point purpose may be related to the equipment type selected using element 1102. In the example shown in FIG. 11B, the user has selected a point purpose of “Temperature”.

Once the user has selected an equipment type or has selected both an equipment type and a point purpose, the user may select a “Filter” button 1106 to filter the list of model classes. Filtering the list of model classes may hide or remove model classes that do not correspond to the select equipment type and/or point purpose. In other words, only model classes that correspond to the equipment type and/or point purpose are populated in interface 1100. In the example of FIG. 11B, the user has filtered the list to only include model classes associated with VAVs, and more particularly with temperature. Accordingly, the list of model classes shown in FIG. 11B is shown to have been filtered to only include “Zone Temperature” and a Zone Temperature Setpoint.” The user may then select a particular model class from the list and select a “Save” button 1110 in order to save the selected model class and assign it to the previously selected point definition. In some cases, the user may select a “Cancel” button 1108 to return to interface 1000 without assigning a model class to a point definition.

Referring back to FIG. 10C, the user's selection of a particular model class via interface 1100 is shown to have been populated in interface 1000, indicating that the user has assigned a model class to the selected point definition. In this example, the user has assigned a model class “ZONE SETPOINT” to a “Zone Air Setpoint” point definition. The user may subsequently choose to modify any of the other point definitions shown. Once model classes are assigned to any of the point definitions selected by the user, the user may select a “Save” button (e.g., one of control elements 1012) to save the changes. Alternatively, the user may select a “Cancel” button to disregard any changes (e.g., assigned model classes).

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products including machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine-readable medium. Thus, any such connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule Based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision step. 

What is claimed is:
 1. A building management system (BMS) comprising: one or more memory devices having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to perform operations comprising: obtaining a BMS ontology data model defining a plurality of BMS model classes and relationships between the BMS model classes; assigning a BMS model class to a plurality of BMS object definitions, wherein the BMS model class is a semantic identifier selected from the plurality of BMS model classes defined by the BMS ontology data model; generating a semantic site model by classifying a plurality of BMS objects associated with a building site according to the BMS object definitions and the BMS model classes assigned thereto; and transmitting a notification using the semantic site model.
 2. The BMS of claim 1, the operations further comprising: presenting, via a graphical user interface, the semantic site model; receiving a user input indicating one or more user defined policies, wherein the user defined policies pertain to the BMS objects; and updating one or more control actions using the user defined policies, wherein the control actions include one or more parameter setpoints.
 3. The BMS of claim 1, the operations further comprising: determining, from a plurality of control actions, an optimal set of control actions using the semantic site model; presenting, via a graphical user interface, the optimal set of control actions; receiving a user input indicating a change to the optimal set of control actions; and updating the optimal set of control actions to include the change to the optimal set of control actions.
 4. The BMS of claim 1, wherein assigning the BMS model class to each of the plurality of BMS object definitions further comprises: receiving a user selection of the BMS model class for each of the BMS object definitions; and assigning the BMS model class to each of the plurality of BMS object definitions based on the user selection.
 5. The BMS of claim 1, wherein the BMS objects associated with the building site include at least one of equipment objects representing specific building equipment and point objects representing specific points in the BMS.
 6. The BMS of claim 1, wherein the BMS objects associated with the building site include space objects representing specific spaces in the building site and wherein the plurality of BMS object definitions further comprise space definitions defining a plurality of different spaces.
 7. The BMS of claim 1, the operations further comprising: obtaining a fault detection rule for the building site, the fault detection rule comprising one or more fault criteria defined without reference to one or more particular BMS objects needed to evaluate the fault criteria; using the semantic site model to identify the particular BMS objects needed to evaluate the fault criteria; and detecting a fault condition by evaluating the one or more fault criteria using data associated with the particular BMS objects.
 8. The BMS of claim 7, wherein evaluating the fault criteria comprises comparing a value provided by one or more of the particular BMS objects against a threshold.
 9. A method comprising: obtaining a BMS ontology data model defining a plurality of building management system (BMS) model classes and relationships between the BMS model classes; assigning a BMS model class to a plurality of BMS object definitions, wherein the BMS model class is a semantic identifier selected from the plurality of BMS model classes defined by the BMS ontology data model; generating a semantic site model by classifying a plurality of BMS objects associated with a building site according to the BMS object definitions and the BMS model classes assigned thereto; and transmitting a notification using the semantic site model.
 10. The method of claim 9, further comprising: presenting, via a graphical user interface, the semantic site model; receiving a user input indicating one or more user defined policies, wherein the user defined policies pertain to the BMS objects; and updating one or more control actions using the user defined policies, wherein the control actions include one or more parameter setpoints.
 11. The method of claim 9, further comprising: determining, from a plurality of control actions, an optimal set of control actions using the semantic site model; presenting, via a graphical user interface, the optimal set of control actions; receiving a user input indicating a change to the optimal set of control actions; and updating the optimal set of control actions to include the change to the optimal set of control actions.
 12. The method of claim 9, wherein assigning the BMS model class to each of the plurality of BMS object definitions further comprises: receiving a user selection of the BMS model class for each of the BMS object definitions; and assigning the BMS model class to each of the plurality of BMS object definitions based on the user selection.
 13. The method of claim 9, wherein the BMS objects associated with the building site include at least one of equipment objects representing instances of building equipment and point objects representing specific points in the BMS.
 14. The method of claim 9, wherein the BMS objects associated with the building site include space objects representing specific spaces in the building site and wherein the plurality of BMS object definitions further comprise space definitions defining a plurality of different spaces.
 15. The method of claim 9, further comprising: determining one or more fault detection rules for the building site; detecting a trigger condition based on the one or more fault detection rules, the trigger condition indicating a fault and a first BMS object associated with the fault; and identifying one or more additional BMS objects associated with the fault based on the semantic data model.
 16. The method of claim 15, wherein the trigger condition comprises an indication that one or more parameters associated with the first BMS object exceed a threshold.
 17. The method of claim 15, wherein determining one or more additional BMS objects associated with the fault comprises: identifying a BMS model class associated with the first BMS object; and identifying the one or more additional BMS objects based on the relationships between the BMS model classes.
 18. A building management system (BMS) comprising: one or more memory devices having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to perform operations comprising: generating a semantic site model by classifying a plurality of BMS objects associated with a building site according to a plurality of BMS object definitions, each BMS object definition comprising an equipment definition defining a type of equipment and at least one point definition defining a type of point, wherein each BMS object definition is assigned a BMS model class selected from a BMS ontology data model; obtaining a fault detection rule for the building site, the fault detection rule comprising one or more fault criteria defined without reference to one or more particular BMS objects needed to evaluate the fault criteria; using the semantic site model to identify the particular BMS objects needed to evaluate the fault criteria; detecting a fault condition by evaluating the one or more fault criteria using data associated with the particular BMS objects; and initiating an automated adjustment of one or more parameters associated with the particular BMS objects in response to detecting the fault condition.
 19. The BMS of claim 18, the operations further comprising: obtaining the BMS ontology data model defining a plurality of BMS model classes and relationships between the BMS model classes, wherein the BMS model classes are semantic identifiers selected from the plurality of BMS model classes defined by the BMS ontology data model.
 20. The BMS of claim 18, wherein the BMS objects associated with the building site include space objects representing specific spaces in the building site and wherein the plurality of BMS object definitions further comprise space definitions defining a plurality of different spaces. 